As explained in SLK Concepts, an attempt is a collection of data that encompasses all information related to one instance of one learner executing one organization of one e-learning package. Each attempt corresponds to one row in the AttemptItem table in the SLK or MLC database. Note that the "attempt" concept is broader than SLK: for example, BasicWebPlayer (MLC sample code) creates attempts even though BasicWebPlayer doesn't implement SLK concepts like "assignment".
When a program manipulates an attempt, it typically does so by creating an in-memory learning session, represented by an instance of the StoredLearningSession class, in one of two ways:
In either case, once an application has acquired an instance of StoredLearningSession, it uses it to perform one or more operations on the attempt. Examples:
Information tracked by MLC that's related to an attempt is stored in a number of database tables—see SLK+MLC Schema. When an attempt has completed, all tables related to the attempt are populated with information about that attempt. Before an attempt is completed, however, the state of an attempt is maintained in a compressed internal form that's not easily accessible to applications. If an application would like to perform SQL-level reporting on an attempt (either directly, or using LearningStore) before the attempt is complete, the application must call StoredLearningSession.ExpandSessionCache.
Note that Class Server content (e.g. .lrm files) are manipulated in a manner generally quite similar to SCORM 1.2 packages.
StoredLearningSession is designed to operate efficiently in a stateless Web application environment. In an ASP.NET-based Web application, a StoredLearningSession instance typically lives no longer than the duration of one Web request: the Web application creates the StoredLearningSession object to perform some set of operations on the attempt (for example, navigation followed by rendering) and then discards the StoredLearningSession.